System and method for simultaneous display of multiple tables

ABSTRACT

In a system and method for displaying hierarchically related data, a processor may display in a single display window of a display device respective representations of a plurality of hierarchically related data records in accordance with the hierarchical relationship, where each of at least two of the representations includes a respective table including a plurality of data columns, and where the display of some of the columns of the tables is in accordance with display settings set based on a determination that columns of different tables correspond to each other for alignment.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of, and claims priorityunder 35 U.S.C. §120 to, U.S. patent application Ser. No. 11/801,670,filed May 9, 2007, the entire contents of which is hereby incorporatedby reference in its entirety.

BACKGROUND

Data can be arranged in an hierarchical fashion by a logical assignmentof various data elements to classes and sub-classes of data. To allow auser to easily search for a particular data element, a tree structure isoften displayed which can be traversed until the sought data element isfound. For example, files arranged in directories and sub-directoriesare often represented visually in such a tree structure.

A data element presented in an hierarchical tree structure is oftenselectable for viewing of particular properties and attributes of thedata element. For example, in response to selection of a file in thetree structure, the file may be opened in a new display window to revealits contents. The contents may include tables of interrelated data. Forexample, a transaction record represented in the tree structure mayinclude, among other tables, a table of personal data of a customer withwhom the transaction was conducted. Further, it is often the case thatdata of one cell of a table represents another sub-table. For example, acustomer may be associated with multiple transactions. A cell indicatingthat the customer is associated with transactions may be selected todisplay a table including transactions data. For example, each row ofthe transactions data table may include data of a respective transactionrecord. To navigate all of the data, a user can traverse the treestructure to find a data element and select it to separately view itscontents, e.g., a table of data.

Contents of different data elements presented in an hierarchical treestructure can include similar tables or table components. However, atmost, conventional computer systems provide for simultaneous display oftwo first hierarchical level tables that are not hierarchically relatedto each other. Further, the extent to which conventional systems providefor a hierarchical display of records that can be expanded to displaycorresponding tables is limited by the constraint that the tables of asame hierarchical level are of the same structure, i.e., they includethe same column types in the same order. Conventional systems do notprovide for presentation of hierarchically related tables in a mannervia which relationships of different tables and table components of lowhierarchical level tables can be visually discerned. In particular,conventional systems do not provide for presentation of differentlystructured tables in a manner via which relationships of the differentlystructured tables can be visually discerned.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram that illustrates components of a systemaccording to an example embodiment of the present invention.

FIG. 2 is a screenshot of a display including nested tables arrangedaccording to an example embodiment of the present invention.

FIG. 3 is flowchart that illustrates a method that may be performed todisplay a plurality of hierarchically related tables withcollapse/expand indicators.

FIG. 4 is a screenshot of a display that identifies alignment ofcorresponding columns of different tables, according to an exampleembodiment of the present invention.

FIG. 5 is a flowchart that illustrates a method that may be performed todetermine whether columns of a table are associated with columns ofother tables for column alignment, according to an example embodiment ofthe present invention.

FIG. 6 illustrates columns set as fixed or variable for alignment ofcorresponding columns of different tables, according to an exampleembodiment of the present invention.

FIG. 7 is a flowchart that illustrates a method that may be performed toarrange columns in a display, according to an example embodiment of thepresent invention.

FIG. 8 illustrates selective alignment of some of a plurality of columnsarranged in different orders in different tables, according to anexample embodiment of the present invention.

FIG. 9 illustrates alignment of pairs of corresponding columns having adifferent number of intermediary columns, according to an exampleembodiment of the present invention.

FIG. 10 illustrates alignment of pairs of corresponding columns having adifferent number of intermediary columns, according to an alternativeexample embodiment of the present invention.

FIG. 11 illustrates partial alignment of pairs of corresponding columnshaving a different number of intermediary columns without alignment ofcolumn edges, according to an example embodiment of the presentinvention.

FIG. 12 illustrates full alignment of pairs of corresponding columnshaving a different number of intermediary columns, according to anexample embodiment of the present invention.

FIG. 13 illustrates a width of a first column set based on maximumallowed white space and based on consideration of correspondence ofanother column of the same table as that of the first column with acolumn of another table, according to an example embodiment of thepresent invention.

DETAILED DESCRIPTION

Embodiments of the present invention relate to a computer system andmethod for improving visualization of hierarchically structured dataelements by providing an expanded tree structure with a visualization ofthe relationship of the different data elements in the tables regardlessof hierarchical level. In particular, embodiments of the presentinvention provide for a display of hierarchically arranged nestedtables. More particularly, embodiments of the present invention providefor the display of the nested tables in a manner that accentuates therelationships of different tables and/or table components of differenttables of the same or different hierarchical levels of the hierarchicalstructure. In an example embodiment of the present invention, for suchaccentuation, columns of different ones of the tables that include thesame type of data may be aligned.

The computer system may include one or more computer programs written inany conventional computer language. Example computer languages that maybe used to implement the computer system and method of the presentinvention may be Java, Extensible Markup Language (XML), C++, StructuredQuery Language (SQL) or other database query language, or a combinationthereof. The computer program(s) may include, e.g., a plurality ofroutines for performance of different tasks.

FIG. 1 is a block diagram that illustrates example components of asystem on which embodiments of the present invention may be implemented.The system may include a memory 100, which may include any combinationof conventional memory circuits, including electrical, magnetic, and/oroptical systems. The memory 100 may include, for example, read onlymemory (ROM), random access memory (RAM), and/or bulk memory.

The memory 100 may include a computer program 101 and a relationaldatabase 102. Information may be stored, e.g., relationally, in thedatabase 102. For example, the information may be stored as a pluralityof data elements. The data elements may include records associated witha plurality of further data elements that can be grouped in multipleways. The further data elements with which the records are associatedmay be further records that are associated with other data elements,etc. A record's sub-records may include different record types. Forexample, an “expense” record may be associated with multiple transactionrecords, each transaction contributing to the expense record, and may beassociated with multiple company records, each company contributing tothe expense. The relationships between various data elements may includedifferent kinds of cardinality. For example, cardinalities may includeone to one, one to many, and/or many to many.

The relational database 102 may store the records as nodes in a datastructure definition. The data structure definition may include nodedefinitions 120, where each node is represents a record. A nodedefinition of a particular node for which one or more tables of data maybe presented may include a node ID 121, a dependency pointer 122pointing to an immediate parent of the particular node, child pointers123, one or more table definitions 125, and table data 124 to bepresented in the columns of the table defined by the table definition125. A record may be stored as a separate node in the node definition120, e.g., if the record is to be presented as its own separate table.Otherwise, the record may be provided as table data of a parent node. Achild pointer 123 of the particular node may be included in theparticular node's node definition to another node that is a child nodeof the particular node having its own defined node structure, if theparticular node has such a child node.

The table definition(s) 125 may include a plurality of column IDs 126,column constraints 127 such as a stipulation of a data type that may beincluded in the column (if there are any such constraints), and columnheaders 128.

The computer program 101 may include a Graphical User Interface (GUI)generator component 116. A processor 105 may execute the computerprogram 101 for obtaining the information or parts thereof from thedatabase 102 and displaying, via execution of the GUI generatorcomponent 116, tables including the obtained information according tothe relationships between the data elements as defined by the nodedefinitions 120, e.g., in accordance with prescribed criteria, forexample, input by a user via an input device 111, e.g., at a terminal110. For example, the GUI generator component 116 may generate differenttables according to different hierarchical data structures 130,depending on which columns defined in the node definitions 120 the userindicates should be included in the provided tables. The processor 105may output data for causing display of the generated tables on a GUI 112provided in a monitor screen of the terminal 110. The memory 100 may bea memory of the terminal 110 or may be, e.g., a server memory thatservices a plurality of terminals. For example, the information of thedatabase 102 may include information input by multiple users viadistributed devices of a network, e.g., the Internet.

The processor 105 may be any one or combination of suitably appropriateprocessing systems, such as, for example, a microprocessor, a digitalsignal processor, and a field programmable logic array. The processingsystem may be embodied as any suitably appropriate computing device,e.g., a computer, personal digital assistant (PDA), laptop computer,notebook computer, a hard-drive based device, or any device that canreceive, send, and store data.

FIG. 2 is a screenshot of a display the processor 105 may display on theGUI 112 via execution of the GUI generator component 116 of the computerprogram 101, according to an example embodiment of the presentinvention. The processor 105 may generate and display on the GUI 112 aplurality of tables that includes tables nested according to thehierarchy in which the data elements are stored in the database 102and/or according to hierarchies specified for the present display, e.g.,depending on user input indicating the particular constraints regardingwhich data to include in the display. Parts of the display may beselectable, e.g., via point and click of a mouse. For example, levels ofnested tables may be expandable and collapsible via selection of recordswithin the tables. The processor 105, via execution of the GUI generatorcomponent 130, may provide for expandable/collapsible selection of thosedisplayed records for which a separate node definition 120 is provided.This may be determined based on the child pointers 123.

For example, in an embodiment of the present invention, the processor105 may display a collapse/expand indicator 202, such as an arrow thatindicates that the record alongside which the arrow is displayed isexpandable. The processor 105 may initially display a single parenttable 205 representing a highest hierarchical level that includes aplurality of records, one or more of which are expandable. In responseto a selection of an expandable record, e.g., via point and click of therecord or of its associated indicator 202, via keyboard entries, and/orvia other input types depending on the particular input device used, theprocessor 105 may update the display to include another table 206, e.g.,in place of or below the selected record and within the table 206'sparent table(s). The newly displayed table 206 may be of a lowerhierarchical level than that of the parent table 205. (Depending on thecardinality structure, the hierarchy may take on various forms, suchthat the roles of parent and child in one hierarchy of the database 102may be reversed in another hierarchy of the database 102. For example,the database may include a plurality of dependency and child pointerversions, where each version is associated with a different view orcontext. Depending on the view selected by the user or context in whichthe user inputs an instruction for display of the tables, the GUIgenerator 116 may generate a particular hierarchical structure inaccordance with the corresponding pointer version. However, furtherdiscussion regarding the nature and structures of the hierarchies is notimportant for an understanding of the present invention).

FIG. 3 is a flowchart that illustrates a method that may be performedduring execution of the GUI generator component 116 for generating theparent table 205 representing the highest hierarchical level. At 300,the GUI generator component 116 may receive a table generation request.In response, the GUI generator component 116 may access the database 102and search the node definitions 120 for a node having a record ID thatmatches one associated with the table of the highest hierarchical level.Starting at a first address of the node definitions 120, the GUIgenerator component 116 may determine, at 302, whether there is a recordID match. If there is not a match, the GUI generator component 116 may,at 304, increment the node definition address by 1, and return to 302 tocheck the record identifier of next node definition. When a match isfound, the GUI generator component 116 may, at 306, display the tabledefined in the node's respective table definition 125 including therespective table data 124.

For displaying the table at 306, the GUI generator component 116 may, at308, determine, for each included record of the table(s) of the nodedefinition 120 of the matched record ID, whether there is a childpointer 123 of the node definition 120 of the matched record ID that isassociated with the particular included record. If there is such a childpointer 123, the GUI generator component 116 may, at 309, include anindicator 202 for the record. The GUI generator component 116 may then,at 310, move on to the next record if any. Otherwise, the GUI generatorcomponent may proceed to 310 without including an indicator 202. Steps304-310 may be performed until each record of the table has beenchecked. The procedure of FIG. 3 may also be performed in response toeach selection of an indicator 202, i.e., the selection may beinterpreted as a table generation request.

In one example embodiment of the present invention, in response to theinput indicating an instruction to expand a record, the system andmethod of the present invention may display a table of a hierarchicallevel that is one level lower than that of the table to which the recordselected for expansion belongs, e.g., so that the user can easily followthe progression through the data hierarchy. The newly displayed tablemay include further expandable records initially displayed in acollapsed state. In an alternative embodiment, in response to expansionof a record of a table of a highest hierarchical level, records of alllower hierarchical levels may be displayed initially in an expandedstate so that the user is provided with all information of the datahierarchy associated in a single hierarchical branch with the recordselected by the user.

In one example embodiment of the present invention, the processor 105may display the arrow indicators 202 pointing in different directions,depending one whether the associated records have been expanded. Forexample, the processor 105 may display an arrow pointing towards theright side of the GUI 112 to indicate that the associated record is in acollapsed state and an arrow pointing downwards to indicate that theassociated record is in expanded state. In response to an instruction toexpand a record, the processor 105 may insert within the table to whichthe record belongs a child table associated with the record and maychange the direction of the arrow.

The number of nesting levels of tables that originate from a root tableand that are displayed by the processor 105 may depend on the particularhierarchical structure of the database 102 followed by the processor105. For example, FIG. 2 illustrates tables nested down to a fourthhierarchical level. However, further levels are possible depending onthe given hierarchy. In one example embodiment of the present invention,the number of different levels of tables simultaneously displayed on theGUI 112 may be limited only by the size of the GUI 112.

In an example embodiment of the present invention, the user may selectany displayed record's indicator 202. In response to the selection, thesystem and method may display the record's associated table, whilemaintaining the previous collapsed/expanded state of all other recordsdisplayed prior to the user selection. Thus, particular expandablerecords of a particular table may be displayed in an expanded statewhile other records of the particular table are simultaneously displayedin a collapsed state. For example, with respect to table 205, record205.B is shown displayed in an expanded state, while records 205.A and205.C are shown displayed in a collapsed state. The expanded recordincluding a table with one or more records may be displayed betweenother records, including expanded and collapsed records, of the table towhich the expanded record belongs. More than one record may be displayedsimultaneously in an expanded state. For example, after performing theprocedure described with respect to FIG. 3 for a first record of a lowhierarchical level, the GUI generator component 116 may receive anothertable generation request with respect to a second record of a lowhierarchical level, e.g., on a different hierarchy branch than that ofthe first record. In response to the new request, the GUI generatorcomponent 116 may update a previously generated display to include a newtable corresponding to the second record for nested display in a parenttable without removing the previously provided table of the first recordfrom the display.

The present invention accommodates nested tables that have differentstructures. For example, a non-exhaustive list of differences mayinclude differences with respect to a number of included columns, datacategories to which the columns correspond, data types included in thecolumns, and/or the order in which the tables' respective columnsappear. For example, the respective structures of tables 205 and 206 areshown to be different at least with respect to the number of includedcolumns and the particular data categories for which correspondingcolumns are provided.

The tables having different structures may be of different hierarchicallevels and/or of the same hierarchical level. With respect to records ofthe same hierarchical level having different table structures, therecords may be of the same or different tables. For example, records207.C and 207.D, which are of the same hierarchical level and whichbelong to the same table, i.e., table 207, are shown as being expandedto tables having different structures. Moreover, a single record may beexpanded to display a plurality of differently structured tables. Arecord may include sub-records expandable to differently structuredtables or may be expanded to display differently structured tables, forexample, where, respectively, the sub-records of the record includedifferent record types, or where the tables include records of differenttypes. For example, an “expense” record may be associated with multipletransaction records, each transaction contributing to the expenserecord, and may also be associated with multiple company records, eachcompany contributing to the expense.

The tables having different structures, whether of the same or differenthierarchical levels and whether of the same or different immediatelypreceding parent tables, may be simultaneously displayed.

In an example embodiment of the present invention, different records ofa same hierarchical level may be expanded to a different number ofsub-hierarchical levels. For example, a first record of a particularhierarchical level may be fully expanded to a number of sub-hierarchicallevels that correspond to a first number, i.e., first with respect tohierarchical sequence, of sub-hierarchical levels of a second record ofthe particular hierarchical level, so that the last of all of thesub-hierarchical levels of the first record may correspond to the lastone of the first number of sub-hierarchical levels of the second record,although the second record may be further expanded to a second number ofsub-hierarchical levels of lower hierarchical level than that of thelast one of the first number of sub-hierarchical levels.

A first record expandable to fewer hierarchical levels than a secondrecord, e.g., of the same table as that of the first record, may bemissing tables corresponding to tables of intermediate ones of thehierarchical levels of the second record, but may include tablescorresponding to tables of hierarchical levels of the second record thatare higher and lower than the intermediate hierarchical levels. Forexample, a first record may represent a company headquarters in chargeof facilities throughout a country. A first sub-hierarchical level ofthe first record may include records representing managers of facilitiesin various regions of the country, each region including a number ofstates. A second sub-hierarchical level, which is a sub-hierarchicallevel of the records of the first sub-hierarchical level, may includerecords representing managers of facilities in particular ones of thestates of the regions represented by their respective parent records. Bycontrast, a second record may represent another company headquarters incharge of facilities throughout the country. A first sub-hierarchicallevel of the second record may include records representing managers offacilities in particular states of the country. A hierarchical levelincluding records representing managers of facilities in regions of thecountry may be omitted with respect to the second record. Thus, althoughtables may be of different hierarchical levels, they may be associatedwith each other. Their simultaneous display may aid the user indiscerning the tables' associations with each other.

Even where different tables that are logically associated with eachother are simultaneously displayed, it can nevertheless be difficult forthe user to visually comprehend the logical data associations, inparticular where the tables are not separated from each by other recordsor where the tables are of different hierarchical levels. In an exampleembodiment of the present invention, a plurality of tables may bedisplayed simultaneously in a manner that accentuates relationshipsbetween data of the plurality of tables. For such accentuation, columnsof different ones of the tables that include data determined to beassociated with each other may be aligned. For example, FIG. 4 is ascreenshot of a display similar to the screenshot of FIG. 2, but furtherindicates where columns of tables 208 and 209 have been alignedaccording to an example embodiment of the present invention. Whethercolumns of different tables are determined to be associated with eachother by the GUI generator component 116 may depend, for example, on thedifferent column IDs 126, column headers 128, and/or column constraints127, as provided in a rule set 136, as explained below.

According to an example embodiment of the present invention, columns ofa plurality of tables of a single record determined to be associatedwith each other may be aligned. According to a further embodiment of thepresent invention, even columns that are of a plurality ofsimultaneously displayed tables of different corresponding records of animmediate parent record's table, and that are determined to beassociated with each other may be aligned. According to a furtherembodiment of the present invention, even columns that are of aplurality of simultaneously displayed tables of different correspondingrecords of tables of different immediate parent records and that aredetermined to be associated with each other may be aligned. According toa further embodiment of the present invention, even columns that are ofa plurality of simultaneously displayed tables of different hierarchicallevels of a data tree and that are determined to be associated with eachother may be aligned.

In one example embodiment of the present invention, columns of differenttables may be determined to be associated with each other if the columnsare assigned the same column header 128. For example, a rule set 135used by the computer program 101 for storing data in the database 102may provide that for a particular table, each column must be assigned anID unique with respect to other columns of the same table, but that thecolumns of different tables may be assigned the same column header 128.

In an alternative example embodiment of the present invention, columnsof different tables may be determined to be associated with each otherif the columns are assigned the same column ID 126. For example, therule set 135 used by the computer program 101 for storing data in thedatabase 102 may provide that for a particular table, each column mustbe assigned an ID unique with respect to other columns of the sametable, but that columns of different tables may be assigned the same ID.Unlike a column header, the column ID may be metadata that is notdisplayed by the GUI generator component 116 in response to a tablegeneration request. Initially when entering the table data to beeventually included in the table display, or when updating the data, theuser may assign the column IDs based on the user's determination thatthere is a relationship between different tables' columns.

Use of column IDs instead of column headers may be advantageous becausecolumns having categorically different data nevertheless may have arelationship to each other. Thus, the column IDs may be used forassociating the columns to each other for purposes of alignment. Theassociation for purposes of alignment may be performed so that arelationship between the columns' respective data may be visuallydiscerned. For example, a table of a first hierarchical level mayinclude a “net worth” column in the cells of which are included dataindicating a respective record's associated company's net worth. Tablesof lower hierarchical levels, which may be displayed by expanding therecords of the first hierarchical level, may include a table having acolumn that includes cells, data of which indicate a particular assetvalue, and a table having a column that includes cells, data of whichindicate a particular debt. The assets and debts may bear a relationshipto the overall net worth represented in a record of the parent table.Accordingly, although the data represented in each of the tables may becategorically different, they may nevertheless bear a relationship forwhich a visual indication may be beneficial and may be provided based onshared column IDs according to an example embodiment of the presentinvention.

In an alternative example embodiment of the present invention, otherfactors in addition to or instead of column ID may be taken into accountfor determining an association between columns of different tables. Forexample, the rule set 136 may provide that the GUI generator component116 is to examine definitions of a data type of columns within differenttables to identify a relationship between the columns. For example, datadefining a number format (e.g., representing dollar amounts) may causethe columns to be considered related even if the column headings and/orIDs do not indicate a relationship. The columns determined to be relatedmay be aligned, which may contribute to a display that is more easilyreviewed by the user.

In one example embodiment, the system and method of the presentinvention may provide for alignment of only those columns that includedata in a number format. In particular, the system and method mayprovide for alignment of only those columns that include data in aparticular number format type, e.g., a dollar amount format. Moreparticularly, the system and method may provide for alignment of onlythose columns dedicated to inclusion of, e.g., only, data that is in thenumber format. Whether a column satisfies these conditions may bediscerned by checking the table data 124 of the column and/or the columnconstraints 127 of the column.

Alternatively or additionally, the system and method of the presentinvention may provide for manual association by a user between columnsof different tables, regardless of an assignment of identical IDs or theinclusion of similar data types. For example, the GUI generatorcomponent 116 may generate a set-up page with a set of drop-down boxespresented in an hierarchy based on the dependency and child pointers 123of the node definitions 120. The drop-down boxes may each correspond toa respective table and may include a list of column names of therespective table. The user may select a column header name and, e.g.,drag and drop it on another drop-down box from which the user may selecta column header name of the column with which the user desires anassociation to the dragged column header name. In response to thedrag-and-drop, the GUI generator component 116 may access the database102 to update the table definition 125 of the node corresponding to thedragged table and the node corresponding to the table at which it wasdropped to include a pointer associated with each of the selectedcolumns to the other selected column. Alternatively, for a displayedcolumn, the user may otherwise input instructions identifying aparticular table and column with which to associate the displayedcolumn. Any other suitably appropriate method of inputting instructionsmay be used for manual association between columns.

The particular conditions that must be satisfied for columns ofdifferent tables to be considered as being associated with each otherfor alignment may be stored in the rule set 136. For each column to bedisplayed, the GUI generator 116 may determine whether the columnsatisfies each condition of the rule set 136.

FIG. 5 is a flowchart that illustrates a method that may be performed bythe GUI generator component 116 to set a column to be displayed as beingone that corresponds for alignment with a column of another table. At500, the GUI generator component 116 may compare the column's ID with acolumn ID of another table to be included in the display to determine ifthere is a match. (Which other tables are to be included in the displaymay depend on which records were selected for expansion by the user.) Ifthere is a match, the GUI generator component 116 may, at 502, store anindication that notes the association of the column with the column ofthe other table. After noting the association, the GUI generatorcomponent 116 may, at 504, determine if the table in which thecorresponding column was found is the last of the tables to be included.If there are other tables, the GUI generator component 116 may, at 506,move on to the first column of the next table to be displayed, andrepeat the steps starting at 500 with respect to the first column of thenext table.

If it is determined at 500 that there is no match, the GUI generatorcomponent 116 may, at 508, determine whether the previously checkedcolumn is the least of the columns of the table. If it is not the lastcolumn, the GUI generator component 116 may, at 508, move on to the nextcolumn of the table and repeat the steps starting at 500 with respect tothe next column. If it is determined at 508 that the checked column isthe last column, the GUI generator component 116 may perform 504. Steps500 to 504 may be performed until it is determined at 504 that thepreviously checked table is the last of the tables to be displayed.

As indicated above, whether columns of different tables correspond foralignment may depend on satisfaction of additional or differentconditions than matching column ID. For each condition, the GUIgenerator component 116 may determine whether a column satisfies thecondition and store a flag indicating whether the condition has beensatisfied. If all flags are set indicating that the column satisfies thecondition. If all flags are set indicating satisfaction of all of theconditions, the GUI generator component 116 may generate the tables sothat the columns satisfying the condition are aligned with the columnsindicated to be ones to which the column corresponds for alignment.

In an example embodiment of the present invention, for arrangement ofcolumns to provide for alignment between tables, the system and methodmay set a column width as either fixed or variable. A fixed column widthis one that is based on the respective column's data, associations foralignment with columns of other tables, and/or rules of the rule set 136regarding permissible column widths for a column. A variable columnwidth is one that is based at least on a remaining space available toneighboring columns or to the respective column's table's edge aftersetting a position and width of the neighboring columns and/or aftersetting edges of the respective column based on correspondence foralignment of the respective column with a column of another table.

A column's width may be set as variable if at least one of threeconditions of the rule set 136, hereinafter referred to as condition 1,condition 2, and condition 3, is met. With respect to condition 1, awidth of a first column of a first table may be set as variable if thefirst column corresponds for alignment with a first column of a secondtable and is positioned to an immediate left of a second column of thefirst table that is designated for alignment with a second column of thesecond table, and the first column of the second table is separated fromthe second column of the second table by an intermediate column. Withrespect to condition 2, a width of a first column of a first table maybe set as variable if the first column does not correspond for alignmentwith any column of any other table and is positioned to an immediateleft of a second column of the first table that is aligned with a columnof another table. With respect to condition 3, a width of a first columnof a first table may be set as variable if the first column correspondsfor alignment with a first column of any other table and is a right-mostof all aligned columns of the first table, and the first column of anyof the other tables to which the first column of the first tablecorresponds is positioned to the left of more columns than is the firstcolumn of the first table. For a column that does not meet any of thethree conditions, the column may be assigned a fixed width.

The three conditions are exemplary. In alternative embodiments of thepresent invention, columns may be set as variable upon satisfyingadditional or alternative conditions. For example, condition 1 may beexpanded to include setting as variable a width of a first column of afirst table if the first column of the first table corresponds foralignment to a first column of a second table and is separated from asecond column of the first table that is the first one of the columns tothe right of the first column of the first table that correspond foralignment to any column of the second table by fewer columns than arethe first column of the second table and the column of the second tableto which the second column of the first table corresponds for alignment.For example, with respect to FIG. 12 (which does not illustrateimplementation of this variant condition 1 for assigning a variantwidth), column 1203 satisfies this variant condition 1. In onealternative example embodiment of the present invention, only a columnto the immediate left of a left most one of the columns of the tablethat corresponds for alignment with a column of another table is set asa variable width column.

FIG. 6 shows assignments of either variable or fixed widths to columnsof a plurality of tables, where the assignments are determined based onwhether any of the three conditions is met.

The width of column 623 is set as variable since column 623 satisfiescondition 1. In this regard, column 623 corresponds for alignment withcolumn 614 and is positioned to the immediate left of column 624 whichcorresponds for alignment with column 616 which is separated from column614 by intermediate column 615. The widths of columns 621, 631, 632,641, 642, and 653 are similarly set as variable since these columnssatisfy condition 1.

The width of column 652 is set as variable since column 652 satisfiescondition 2. In this regard, column 652 does not correspond foralignment with columns of any of the other tables 600-660 and ispositioned to the immediate left of column 653 which corresponds foralignment with columns 604, 614, 623, 642, and 665. The width of column663 is similarly set as variable since this column satisfies condition2.

The width of column 616 is set as variable since column 616 satisfiescondition 3. In this regard, column 616 corresponds for alignment withcolumns 606, 624, 643, 654, and 667. Column 616 is a right-most of allaligned columns of table 610, and columns 606 and 667 are eachpositioned to the left of more columns than is column 616. The widths ofcolumns 624, 633, 643, and 654 are similarly set as variable since thesecolumns satisfy condition 3.

The widths of the remaining columns 601-607, 611-615, 622, 651, 661-662,and 664-668 are set as fixed since these columns do not satisfy any ofthe three conditions.

FIG. 7 illustrates a method for arranging a display of columns in whichcorresponding columns may be aligned, according to an example embodimentof the present invention. The system and method may initially, at 700,determine whether the column corresponds for alignment with a column ofanother table. For example, the method described with respect to FIG. 5may be performed at this point. However, additional conditions besidesfor matching column ID may also be considered, such as data type of thecolumn. Furthermore, as discussed in detail below, table displayconstraints, in particular in view of association for alignment betweenother columns may impact whether the GUI generator component 116 sets acolumn as corresponding for alignment with other columns. Accordingly,after setting a tentative indication that columns correspond foralignment with columns of other tables, the system may determine for afirst column having a tentative indication that it corresponds foralignment with another column whether the indication should be finalizedbased on the tentative indications of other columns.

After determining, for each of the columns to be displayed, whether thecolumn corresponds for alignment with a column of another table, thesystem may, at 702, determine for each column whether the column's widthshould be set as variable or fixed, e.g., by determining whether thecolumn satisfies any of the three conditions. For example 702 mayinclude 703-707.

At 703, the system may determine whether a column satisfies condition 1.If it satisfies condition 1, the system may, at 706, set the column'swidth as variable. If it does not satisfy condition 1, the system may,at 704, determine whether the column satisfies condition 2. If itsatisfies condition 2, the system may proceed to 706. Otherwise, thesystem may, at 705, determine whether the column satisfies condition 3.If it satisfies condition 3, the system may proceed to 706. Otherwise,the system may, at 707, set the column width as fixed.

After the determination whether to set the column width as fixed orvariable is made for each column, the system and method may, at 708,set, for each fixed width column, the column's width to the lesser of(a) the maximum allowed column width and (b) the width required fordisplay of all of the data of the cell(s) of the column (and allcorresponding columns of other tables if any) that includes the greatestamount (with respect to required display space) of data. In analternative example embodiment, 708 may be performed during 702 aftereach determination that a column should be fixed.

After the widths of the fixed width columns are set, the system andmethod may set the positions for each column. For setting the columns'positions, the system and method may, at 709, set positions for thefixed width columns of all of the tables and may then, at 710, setpositions for the variable width columns of all of the tables. To setthe positions of the fixed width columns of a table, the system andmethod may begin with the right-most fixed width column of the table andmove onwards towards the left of the table.

To set the position of a fixed width column, if the column is aright-most column of the table, its right edge may be set at the rightedge of the table. Its left edge may be set at a position that is at adistance from the column's right edge that corresponds to the column'sset column width.

If the fixed width column is not the right-most column of the table andthe position of the left edge of the column to its immediate right hasbeen set, its right edge may be set at the left edge of the column toits immediate right. Its left edge may be set at a position that is at adistance from the column's right edge that corresponds to the column'sset column width.

If the fixed width column is not the right-most column of the table andthe position of the left edge of the column to its immediate right hasnot been set, its left edge may be set at the first column position forfixed width columns of the table if it is the left-most fixed widthcolumn of the table. The first column position may be tentatively set inaccordance with a display area determined by the equation

$\left\lbrack {\left( {\max*{var\_ width}{\_ col}{\_ no}} \right) + \left( {\max*{var\_ width}{\_ cond}\; 1{\_ no}} \right) + \left( {\max*{\sum\limits_{n = 0}^{x}\;{{no\_ right}{\_ cor}{\_ col}{\_ cond}\; 3(n)}}} \right) + {\sum\limits_{n = 0}^{m}{{width}\mspace{14mu}{of}\mspace{14mu}{fixed\_ width}{\_ col}(n)}}} \right\rbrack,$where max is the maximum width of all of the tables' fixed columns'widths, var_width_col_no is the number of columns of the table that arevariable, var_width_cond1_no is the number of columns of the table thatsatisfy condition 1, no_right_cor_col_cond3(n) is the number of columnsto the right of a column that corresponds to the variable column ‘n’ ofthe table satisfying condition 3 and that is of a table having the mostnumber of columns to the right of any table's column corresponding tothe column ‘n,’ x is the number of columns of the table satisfyingcondition 3, and m is the number of fixed width columns of the table.Once the tentative display area is determined, the left edge of thefixed column may be positioned at a distance from the first columnposition of the table that equals ([max] *[number of columns to thefixed width column's left]). Its right edge may be set at a positionthat is at a distance from the column's left edge that corresponds tothe column's set column width.

The calculated display area may be larger than actually necessary. Inone example embodiment of the present invention, subsequent topositioning of all of the columns, the system and method may adjust thepositioning to provide a smaller display area. In an alternativeembodiment, the larger display area may be maintained. In anotheralternative embodiment, instead of applying ‘max’ as the width for allof the variable width columns of the table, the calculation of thedisplay area and the portion of the display area required to the left ofthe fixed column to be positioned may be fine tuned to the particularfixed column widths of the fixed columns on which are based the widthsof the variable width columns of the table.

If the fixed width column is not the right-most column of the table, theposition of the left edge of the column to its immediate right has notbeen set, the fixed width column is not the left-most fixed width columnof the table, and the column corresponds for alignment with a column ofanother table the position of the left edge of which has already beenset, its left edge may be set at the horizontal location of the displaycorresponding to the horizontal location of the set left edge of thecolumn to which the fixed width column corresponds for alignment. Itsright edge may be set at a position that is at distance from thecolumn's left edge that corresponds to the column's set column width.

If the fixed width column is not the right-most column of the table, theposition of the left edge of the column to its immediate right has notbeen set, the column is not the left-most fixed width column of thetable, and the column does not correspond for alignment to a column ofanother table the position of the left edge of which has already beenset, the system and method may seek a next column to the left of thefixed width column which is itself fixed and which corresponds foralignment with a column of another table the position of the left edgeof which has been set or which is the left most fixed width column ofthe table. If such a next column is found, the system and method may setthe position of the found column. The system and method may then set,based on assigned widths, all fixed width columns that consecutivelyfollow the found column to the right of the found column withoutinterruption by variable width columns. If there are only variablecolumns to the left of the fixed width column or if there is a variablewidth column between the found column and the fixed width column, thesystem and method may interrupt setting a position for the fixed widthcolumn, and move on in the table to the left of the found column to thenext fixed width column for which positions have not yet been set, ifany. If positions of any of the fixed width columns to the left of thefound column can be set as described above, the system and method may doso. Once all of the fixed width columns of the table, the positions ofwhich can be set as described above, have been set, the system andmethod may interrupt setting the positions of the fixed width columns ofthe table and move on to setting fixed width columns of followingtables.

After performing these steps for all of the tables, the system andmethod may return to the tables including fixed width columns for whichpositions were not determined in the previous loop through the methodand attempt to set the positions of the fixed width columns for whichpositions were not previously set. The loop may be repeated until thepositions of all of the fixed width columns have been set.

After all of the positions are set for all columns having fixed columnwidths, the system and method may set the positions of the columnshaving variable column widths. The system and method may begin at theright most column of a table and continue towards the left. If avariable width column is a right most column of a table, the system andmethod may set its right edge at the right edge of the table. If thevariable width column is not a right most column of the table, thesystem and method may set its right edge at a left edge of the column toits immediate right.

With respect to the left edge of the variable width column, if thecolumn to the immediate left of the variable width column is a fixedwidth column, the system and method may set the left edge of thevariable width column at the right edge of the fixed width column to theimmediate left of the variable width column.

If the column to the immediate left of the variable width column isitself a second variable width column, then the first variable widthcolumn is variable for the reason that it satisfies either condition 1or condition 3, i.e., the first variable width column corresponds foralignment with a column of at least one other table. (The first variablewidth column does not satisfy condition 2, since, if it did, the columnto its immediate left would have been fixed.) Accordingly, the systemand method may search other tables for a column to which the firstvariable width column corresponds for alignment and the left edge ofwhich had been previously set. For example, the column of the othertable may be a fixed width column, the position of which had been setprior to setting of the variable width columns, or may be anothervariable width column the left edge of which has been set, e.g., basedon the right edge of a fixed width column to its immediate left or basedon another previously set column to which the other variable widthcolumn corresponds.

In one example embodiment of the present invention, if the variablewidth column is a left most column of the table and does not correspondfor alignment with a column of any other table, the system and methodmay postpone setting the position of the left edge of the variable widthcolumn until after positions of left edges of all of the columns of allof the tables, but for left most variable width columns, have been set.At this point, a first column position of each table may be determinedIn an alternative example embodiment of the present invention, thesystem and method may postpone setting the position of the left edge ofthe variable width column until after positions of the left edges of allof the columns of all of the tables of the same hierarchical level asthat of the table to which the variable width column belongs, but forthe left most variable width columns, have been set. According to thisalternative, tables of different hierarchical may have different columnstarting positions, at least if first columns of tables of differenthierarchical levels do not correspond for alignment. In an alternativeexample embodiment of the present invention, each table may have its owndefined first column starting position. According to this alternative,if a first column of a table is a variable width column that does notcorrespond for alignment with any other column, the system and methodmay set a width for the column as the lesser of (a) the predeterminedmaximum allowed column width and (b) the width required for simultaneousdisplay of all of the data of the cell(s) containing the greatest amount(with respect to required display space) of data of all of the cells ofthe column. The left edge of the variable width column may be set inaccordance with the determined width. In an alternative exampleembodiment of the present invention, condition 2 may be limited to onlythose columns that are not left most columns of their respective tables,in which case the column's position would be set as described above withrespect to fixed width columns.

An example implementation of some of the features of the methoddescribed above may be described with respect to FIG. 6. With respect toFIG. 6, after determining for each column whether the column is avariable or fixed width column and setting the widths of the fixed widthcolumns, the system and method may begin to set positions of the columnsof table 600. Since all of the columns of table 600 are fixed widthcolumns, their positions may be set during an initial pass through themethod. The system and method may then proceed to column 615 of table610, since it is the right most fixed width column of table 610. To setthe column's position, the system and method may set the left edge ofcolumn 615 to the same horizontal position of the left edge of column605. The right edge of column 615 may be set to the position at adistance from the column's left edge that corresponds to the column'sset fixed distance. The rest of the columns of table 610 to the left ofcolumn 615, which are all fixed width columns, may be set based on theposition of each column's neighboring column to the right.

The system and method may then set the position of column 622 of table620 in accordance with the position of the left edge of column 613 oftable 610. The position of column 651 of table 650 may be set inaccordance with the position of the left edge of either of columns 601and 611. The system and method may then set the positions of columns668-664 since they are all fixed width columns and are the right mostcolumns of table 660. The system and method may then set the position ofcolumn 661 based on the position of the left edge of any of columns 601,611, and 651. After setting the position of column 661, the system andmethod may set the position of column 662 so that its left edge is atthe right edge of column 661.

The positions of all of the fixed width columns having been set, thesystem and method may begin setting positions of the variable widthcolumns. The right edge of column 616 may be set at the right edge oftable 610. The left edge of column 616 may be set at the right edge ofcolumn 615. The right edge of column 624 may be set at the right edge oftable 620. The left edge of column 624 may be set at the same horizontalposition as that of either of columns 606 and 616. The right edge ofcolumn 623 may be set at the left edge of column 624. The left edge ofcolumn 623 may be set at the right edge of column 622. The right edge ofcolumn 621 may be set at the left edge of column 622. The left edge ofcolumn 621 may be set at the same horizontal position as that of theleft edge of either of column 601 and column 611.

With respect to table 630, the positions of columns 633-631 may besimilarly set based on, e.g., the positions of columns 615, 613, and611, respectively. With respect to table 640, the positions of columns643-641 may be similarly set based on, e.g., the positions of columns616, 614, and 611, respectively. With respect to table 650, thepositions of columns 654 and 653 may be similarly set based on, e.g.,the positions of columns 616 and 614, respectively. The position ofcolumn 652 may be set based on the positions of columns 653 and 651.With respect to table 660, the position of column 663 may be set basedon the positions of columns 664 and 662.

In an alternative example embodiment of the present invention, thesystem and method may initially set positions of columns of each tablewithout consideration of positions of corresponding columns of othertables. During the initial positioning, a temporary column width, e.g.,a predetermined minimum column width, may be assigned to variable widthcolumns of the table. After positioning of all of the columns of alltables, column positions may be adjusted based on inter-table columncorrespondence.

In an alternative example embodiment of the present invention, thewidths of all tables that correspond for alignment with columns of othertables may be set as fixed. For example, setting of a variable columnwidth may be limited to those columns satisfying condition 2.

According to this embodiment, if a first column of a first tablesatisfies condition 1, i.e., (a) it corresponds for alignment with afirst column of at least one second table and is positioned to the leftof a second column that corresponds for alignment with a second columnof the at least one second table, and (b) the at least one second tableincludes more intermediate columns between its respective first andsecond columns than does the first table, the width of the first columnof the first table may be set as fixed. To determine its width, thesystem and method of the present invention may determine which of the atleast one second table includes the most intermediate columns. The widthmay then be set based on a width required for display of the contents ofeach of the first columns of the first table and any other tables'corresponding first columns plus the widths of each of the intermediatecolumns of the table determined to include the most intermediatecolumns. For example, referring to FIG. 6, the width of column 621 maybe set as fixed. Its width may be set to be wide enough tosimultaneously display all of its contents and all of the contents ofeach of columns 601, 611, 631, 641, 651, and 661, plus the width ofcolumn 602 or 612 which are each an intermediate column separating,respectively, columns 601 and 603, and columns 611 and 613, wherecolumns 603 and 613 correspond for alignment with column 622.

According to this embodiment, if a first column of a first tablesatisfies condition 3, i.e., it corresponds for alignment with a firstcolumn of at least one second table, is a right-most of the firsttable's aligned columns, and one or more of the at least one secondtable includes additional aligned columns to the right of its respectivefirst column, the width of the first column of the first table may beset as fixed. To determine its width, the system and method of thepresent invention may determine which of the at least one second tableincludes the most aligned columns to the right of its respective firstcolumn. The width of the first column of the first table may then be setbased on its contents and the contents of the corresponding columns ofthe other tables plus the widths of all of the aligned columns to theright of the first column of the one of the at least one second tableincluding the most aligned columns to the right of its respective firstcolumn. For example, referring to FIG. 6, the width of column 633 may beset as fixed. Its width may be set based on the size of its contents andall other columns ‘E’ plus the widths of either columns 605-607 or666-668.

In one example embodiment of the present invention, alignment of columnsof different tables may be limited to different tables having the sameor similar structure, e.g., having the same number of columns, same datacategories to which the columns correspond or same column IDs, and/orsame order in which the tables' respective columns appear. For example,tables 208 and 209 of FIG. 4, the columns of which are aligned, includethe same number of columns, having the same column headers, ordered inthe same way. According to this embodiment, columns of different tablesthat are aligned with each other may be set to a same column size. Forexample, the column width of all columns of a set that are aligned witheach other may be set based on a largest data string included in thecells of all of the set of columns combined.

In an alternative example embodiment of the present invention, columnsof tables having different column structures may also be aligned.However, the extent of implementable column alignment betweennon-similarly structured tables may be limited as detailed below.

According to this embodiment, it may occur that two tables include morethan one pair of columns associated with each other for alignment andthat the tables' respective columns belonging to the column pairs occurin different orders. For example, referring to FIG. 8, column 802 oftable 800 and column 803 of table 801 are assigned a same column ID (orcolumn header) ‘A’ and column 804 of table 800 and column 805 of table801 are assigned a same column ID ‘B’. However, the column A and B ofthe different tables 800 and 801 appear in reverse order. In thisinstance, according to an example embodiment of the present invention,one of the pairs of the associated columns may be aligned, while theother pair may remain unaligned as shown in FIG. 4.

The rule set 136 according to which the system and method of the presentinvention align columns of different tables may provide for maximizingthe number of columns that are aligned with corresponding columns ofanother table. For example, columns of different tables that areassociated with each other with respect to alignment, e.g., where theyshare IDs, may be arranged in different sequences by the nodedefinitions 120. The out-of-sequence column pairs may include sets ofin-sequence column pairs. Further, the different in-sequence column pairsets may include different numbers of column pairs. In this instance,the rule set 136 may provide that the set having the larger number ofin-sequence column pairs is to be aligned and the set having the smallernumber of in-sequence column pairs are not to be aligned. For example,in FIG. 8, the tables 800 and 801 include two sets of columns associatedfor alignment, i.e., set 810 including column pairs B-B (804-805) andC-C (806-807) and set 811 including column pair A-A (802-803). Since set810 includes more pairs of columns associated for alignment than doesset 811, the rule set 136 may provide for alignment of the columns ofset 810, while leaving the columns of set 811 unaligned.

However, the rule set 136 may identify a plurality of conditions otherthan the number of in-sequence column pairs, to be considered fordetermining which sets of column pairs are to be aligned. For example,the rule set 136 may attach particular significance to columnsdesignated for or that are determined to include data having a numberformat. Numbers may be significant with respect to column alignmentsince numbers are often compared, e.g., to determine or discern theparticular transaction amounts of a plurality of tables that are summedto a total amount shown in yet another table. To attach moresignificance to satisfaction of one condition than to satisfaction ofanother feature, the rule set 136 may assign different weights for eachsatisfied condition. For each alignment option, an overall score may becalculated by adding the different weights associated with the alignmentoption. According to this embodiment, the rule set 136 may provide thatthe columns of set 811 should be aligned at the expense of thenon-alignment of the pairs of columns of set 810 if the columns 802 and803 include data in a number format and none of the columns of the set810 include data in the number format (or if none of the pairs of theset 810 includes two columns that each includes data in the numberformat). The rule set 136 may provide for alignment of the set of columnpairs that includes the most columns including data in a number format.This is just one example of a condition that the rule set 136 mayprovide for determining which set of column pairs to align.

Even of those sets of inter-table column pairs that appear in a samesequence in each of the tables, it may occur that each table includes adifferent number of columns that are not associated for alignment withthe other table and interspersed amongst the columns that are associatedfor alignment, than the set of the other table. For example, FIG. 9shows a table 900 that includes columns 902 and 904 that are associatedfor alignment with columns 903 and 905, respectively, of table 901.However, while columns 902 and 904 are positioned next to each otherwithout interruption, columns 903 and 905 are separated by column 906which is not associated for alignment with any column of table 900.

In one example embodiment of the present invention, where twoconsecutive columns of a first table are associated for alignment withtwo non-consecutive columns of a second table that appear in the sameorder as that of the two consecutive columns of the first table, thesystem and method may provide for aligning either the first or thesecond of the two consecutive columns of the first table with thecorresponding column of the second table, without aligning the othercorresponding columns. The two aligned columns may be assigned the samecolumn width.

According to an alternative example embodiment of the present invention,the system and method may provide for aligning both of the associatedcolumns with each other, by aligning at least a portion of thecorresponding columns to each other. For example, as shown in FIG. 9,the outer edges of each of the pairs of corresponding columns may bealigned. FIG. 10 shows alignment of the outer edges of suchcorresponding pairs of columns according to an alternative exampleembodiment of the present invention. In FIG. 10, a left one of theconsecutive pair of columns, i.e., column 1002 of table 1000, isassigned a width so that it is fully aligned with corresponding column1003 of table 1001, while the right one of the consecutive pair ofcolumns, i.e., column 1004 of table 1000, is assigned a width such thatits right edge is aligned with the right edge of corresponding column1005 of table 1001 but its left edge is aligned with the left edge ofthe intermediary column 1006 of table 1001. In a variant of thisembodiment, the right column of the column pair that does not includeany intermediary columns may be fully aligned with its correspondingcolumn and the left column of the column pair that does not include anyintermediary columns may be aligned at its left edge with itscorresponding column and at its right edge with the right edge of theintermediary of the table including the corresponding pair of columns.An exemplary implementation of this variant is described in detail abovewith respect to FIG. 6.

In one variant of this embodiment, the system and method may providethat at least one of the column pairs should not be aligned in certaininstances. For example, the rule set 136 may provide that columns are tobe assigned at least a minimum column width. The minimum may be absoluteor may be relative to the space occupied by the data of the columns. Therule set 136 may further provide that a column width should not exceed acertain maximum width. The maximum may be absolute or may be relative tothe space occupied by the data of the columns. For example, the rule set136 may set a maximum for an amount of white space that may appear aftera longest string of a column. According to this embodiment, the rule set136 may provide for an alignment different than that shown in FIG. 9 ifthe alignment of FIG. 9 requires an assignment to either of columns 902and 904 of a column width greater than the maximum allowed column width.In one variant, the maximums and minimums may be modified according tomanual manipulation of the column sizes. For example, if a user manuallystretches a column's width so that it exceeds its maximum width, therule set 136 may provide for setting a new maximum width as somepredetermined amount past the point to which the user manually extendedthe column's width. Accordingly, if the width required for the column tohave a side aligned with a corresponding column of another table iswithin the predetermined amount past the manually extended edge of thecolumn, the rule set 136 may provide for automatically further extendingthe column so that one of its edges is aligned with an edge of thecorresponding column. Similarly, if the user manually minimizes a columnwidth past its minimum, a new minimum may be set in order to align thecorresponding columns. Even according to this embodiment, however, therule set 136 may set overall absolute maximums and minimums that maytrump the predetermined additional extending or narrowing of thecolumns.

In one variant of this embodiment, while the rule set 136 may providefor generally setting a column's width so that all of the data of mostor all of the column's cells are displayed without scrolling within thecells, the rule set 136 may provide otherwise to minimize the widths ofthe non-consecutive columns towards their respective minimums so thatthe consecutive columns, e.g., extended towards their respectivemaximums, can be aligned at least at their outer edges with thenon-consecutive columns.

It may occur that, even with the minimizing of the column widths of thenon-consecutive columns to their respective minimums and the maximizingof the column widths of the consecutive columns to their respectivemaximums, none of the column edges of the corresponding columns of thedifferent tables become aligned. Nevertheless, the rule set 136 mayprovide for the minimizing of the column widths of the non-consecutivecolumns to their respective minimums and the maximizing of the columnwidths of the consecutive columns to their respective maximums so thatthe corresponding columns may be aligned at least to the extent thatportions of the corresponding columns overlap, e.g., as much aspossible, as shown in FIG. 11. In FIG. 11, of corresponding columns A1102 and 1103 of tables 1100 and 1101, only portions 1102.1 and 1103.1overlap and none of the column edges of columns 1102 and 1103 arealigned. Similarly, of corresponding columns B 1104 and 1105 of tables1100 and 1101, only portions 1104.1 and 1105.1 overlap and none of thecolumn edges of columns 1104 and 1105 are aligned.

In an example embodiment of the present invention, if: (a) a first pairof columns of a first table correspond for alignment to a second pair ofcolumns of a second table; (b) the corresponding columns of the firstpair and the second pair are in the same sequence; and (c) the first andsecond pairs of columns include a different number (of at least oneeach) of intervening columns that are not aligned between the first andsecond tables, the system and method of the present invention mayprovide for fully aligning each of the columns of one pair with therespective corresponding columns of the other pair, i.e., the outeredges of each of the columns of one pair align with the outer edges ofeach of the respective corresponding columns of the other pair. FIG. 12shows an example of pairs of corresponding columns of different tableshaving different numbers of intervening columns. In FIG. 12, column A1202 of table 1200 corresponds to column A 1203 of table 1201, andcolumn B 1204 of table 1200 corresponds to column B 1205 of table 1201.However, between columns 1202 and 1204 of table 1200 are two interveningcolumns 1206 and 1208 that do not correspond for alignment purposes withany columns of table 1201, and between columns 1203 and 1205 of table1201 is only a single intervening column 1207 that does not correspondfor alignment purposes with any column of table 1200. Thus, the numberof intervening columns between columns 1202 and 1204 and between 1203and 1205, respectively, differs. In this instance, columns A 1202-1203and columns B 1204-1205, respectively, are shown to be fully aligned.For the full alignment, the widths of columns 1206 and 1208 may beminimized towards their respective minimums.

In one example embodiment of the present invention, the full alignmentmay be provided only so long as rules regarding the minimum and maximumcolumn widths are adhered to with respect to the intervening columns.Furthermore, whether the full alignment is provided may be impacted bythe extent to which the intervening columns correspond for alignmentwith columns of other tables besides for the first and second table.

Tables including corresponding columns may be structured such that,should all of the corresponding columns of the tables be fully aligned,a first column, e.g., following a column identifying the individualrecords with which the respective rows are associated, of one of thetables would begin after much white space measured from a left edge ofthe table. For example, the full alignment may require that thebeginning of the first column appear in the display screen only afterscrolling the display screen even where the left edge of the table isdisplayed near the left edge of the display area of GUI 112. This mayoccur, for example, where a first table includes a number of columnsthat do not correspond for alignment to any columns of a second table,the non-corresponding columns precede columns that do correspond foralignment to columns of the second table, and the first column of thesecond table corresponds for alignment to a column of the first table.For the alignment of the first column of the second table with thecorresponding column of the first table, it may be required to positionthe first column of the second table so that it begins after white spacecorresponding to the space of the first table in which the number ofnon-corresponding columns are displayed.

In one example embodiment of the present invention, the rule set 136 mayspecify a maximum amount of white space that may precede a beginning ofa first (in sequence) displayed column of a first table, e.g., a columndisplayed first after a column identifying the table records. Fordetermining the amount of required white space, the first white spacebeginning from a left edge of the first table or beginning from a rightedge of a column of the first table in which record identifiers aredisplayed may be considered the beginning of the white space.Accordingly, should alignment of a first column of a first table with acolumn of a second table require displaying a first edge, e.g., a leftedge, of the first column after more than the specified maximum of whitespace, the rule set 136 may provide for displaying the first columnwithout aligning it with the column of the second table. However, evenif the left edge of the first column is not aligned with a left edge ofthe column of the second table, the rule set 136 may provide forextending the width of the first column so that at least the right edgeof the first column aligns with a right edge of the column of the secondtable or so that at least a portion of the first column aligns with aportion of the column of the second table. However, if the rule set 136specifies a maximum width for the first column and the first column doesnot at all align with the column of the second table even if extended tothe maximum allowed width, the rule set 136 may provide for displayingthe first column without extending it for alignment purposes. In onevariant, however, the first column may be extended towards or to themaximum allowed width if such extension allows another column of thefirst table to be aligned, e.g., fully, with a corresponding column ofthe second or another table.

For example, in FIG. 13, column A 1303 of table 1301 may correspond foralignment to column A 1302 of table 1300. However, alignment of columnsA 1302-1303, even to the extent that only portions of the correspondingcolumns overlap without alignment of any edges, may require displaying aleft edge of column A 1303 after a significant amount of white spacethat exceeds a specified maximum since column A 1303 is a first columnof table 1301 and column A 1302 is displayed after columns C 1306 and D1308 of table 1300. Accordingly, the rule set 136 may provide that thecolumns 1303 and 1302 should not be aligned. Portion 1303.1 of column1303 represents a width that would be assigned to column 1303 if onlycontents of column 1303 are considered. Nevertheless, the rule set 136may provide that column 1303 should be extended, towards or to itsmaximum allowed width to include portion 1303.2 so that columns B1304-1305 may be fully aligned.

In an example embodiment of the present invention, a display arearequired for display of all of the columns of all of the tables may belarger than that which can be simultaneously displayed in the displayarea of the GUI 112. For example, the required display area may dependon font size, set column widths, and a number of columns to be providedin a table. Accordingly, after all of the column positions aredetermined, a required scrolling extension to the display area may bedetermined.

In one example embodiment of the present invention, where a scrollingarea is provided, the system and method may set all columns of a table,but for a first column identifying records, to scroll. The first columnidentifying records may remain stationary so that it is always displayedeven when scrolling to view columns to the right. For example, thecolumns scrolling left when scrolling to view columns to the right mayappear to be scrolling into a position underneath the first column.

In an example embodiment of the present invention, subsequent to anarrangement of two (or more) columns of different tables according to astored setting of an association between the two columns, where thecolumns are fully aligned, the system and method may provide that, if auser manually shifts an edge of a column of a first one of the tables,then the corresponding edge of a corresponding column of a second one ofthe tables is automatically shifted in a corresponding manner. In onevariant, the corresponding shift of the column of the second table maybe performed conditional upon maintaining other realized alignmentsbetween the columns of the second and the first table and/or the columnsof the second and other tables, where the other realized alignments arein accordance with stored associations between the aligned columns.Whether the other alignments can be maintained may depend, for example,on the rules regarding maximum and minimum widths, maximum white space,and/or other rules of the rule set 136. In one variant, as long as atleast partial alignment between the other columns can be maintained, thesystem and method may automatically shift the edge of the column of thesecond table in accordance with the manual shift of the edge of thecolumn of the first table. In one variant, the system and method mayshift one or more edges of the column of the second table in accordancewith the manual shift of the column of the first table only to an extentrequired to maintain at least partial alignment between the two columns.In particular, this variant may be implemented in a case where the shiftof the column of the second table to maintain full alignment between thetwo columns causes a loss of full or at least partial alignment betweenother columns.

In one example embodiment of the present invention, the system andmethod may perform the method described with respect to FIG. 7 each timean instruction to modify the display of the tables is received. Forexample, the method may be performed each time an indicator 202 isselected indicating to either expand or collapse a record, or each timeinput for manual manipulation of column edges is received. In analternative example embodiment of the present invention, after a firstdisplay of tables according to the method described with respect to FIG.7, the system and method may adjust the previous table display accordingto the newly received instructions.

Those skilled in the art can appreciate from the foregoing descriptionthat the present invention can be implemented in a variety of forms.Therefore, while the embodiments of this invention have been describedin connection with particular examples thereof, the true scope of theembodiments of the invention should not be so limited since othermodifications will become apparent to the skilled practitioner upon astudy of the drawings, specification, and following claims.

What is claimed is:
 1. A computer-implemented method for displayinghierarchically related data, comprising: simultaneously displaying, by acomputer processor in a display window, respective representations of aplurality of hierarchically related data records in accordance with thehierarchical relationship; wherein: each of at least two of therepresentations includes a respective table, the respective tableincluding: a respective plurality of data columns; a respective columnheader row that includes column headers identifying a respectiveplurality of categories to which the data columns correspond; and one ormore respective additional rows including data indicated to beassociated with the categories of the respective column header row ofthe table to which the plurality of additional rows belongs by displayof the data beneath the column headers of the respective column headerrow; the at least two representations' represented data records dependfrom a common ancestor data record; the respective tables are displayed(a) nested in another table representing the ancestor data record, and(b) such that the respective tables span columns of the another tablewith which data of the respective tables are unassociated; the anothertable representing the ancestor record includes a single column headerrow, displayed simultaneously with the column header row of at least oneof the at least two representations, and that includes column headersidentifying a respective plurality of categories to which the columns ofthe another table correspond; the another table includes a data row that(a) includes data populating fields formed by an intersection of thedata row of the another table with the columns of the another table and(b) is displayed below the at least one of the at least tworepresentations; and the single column header row is displayed above thetables of the at least two representations and is not repeated below anyof the at least two representations.
 2. The method of claim 1, whereinthe respective tables differ from each other with respect to at leastone of a number of included columns, data categories represented byrespective columns, data types included in respective columns, and anorder in which respective columns are arranged.
 3. The method of claim1, wherein a displayed representation includes a plurality of tables,each table including data records of a hierarchical level that is onelower than that of the data record represented by the displayedrepresentation.
 4. The method of claim 1, further comprising:displaying, for each of at least one of the hierarchically related datarecords, a control to toggle between an expanded and collapsed view ofthe respective one of the respective data records; wherein: when theexpanded view is active, a table including child data records of therespective data record is displayed; and when the collapsed view isactive, the table is not displayed.
 5. The method of claim 1, whereinthe columns of the another table correspond to respective datacategories, such that inclusion of data within the respective columnsindicates an association of the included data with the respective datacategories, and the respective tables do not include data belonging tothe respective data categories.
 6. The method of claim 1, wherein thecolumns of the another table correspond to respective data categories,such that inclusion of data within the respective columns indicates anassociation of the included data with the respective data categories,and the display of the respective tables does not indicate anassociation of data of the respective tables with the respective datacategories.
 7. The method of claim 1, wherein the respective tables aredisplayed such that each of the respective tables spans multiple columnsof the another table.
 8. The method of claim 1, wherein the anothertable is displayed in a frame and each of the at least tworepresentations is displayed in a respective frame that is offset fromthe frame of the another table and that graphically separates the atleast two representations from the another table.
 9. Acomputer-implemented method for displaying hierarchically related data,comprising: simultaneously displaying, by a computer processor and in adisplay window, respective representations of a plurality ofhierarchically related data records in accordance with the hierarchicalrelationship, wherein: each of at least two of the representationsincludes a respective table, the respective table including: arespective plurality of data columns; a respective column header rowthat includes column headers identifying a respective plurality ofcategories to which the data columns correspond; and one or morerespective additional rows including data indicated to be associatedwith the categories of the respective column header row of the table towhich the plurality of additional rows belongs by display of the databeneath the column headers of the respective column header row; the atleast two representations' represented data records depend from a commonancestor data record; and the respective tables are displayed (a) nestedin another table representing the ancestor data record, and (b) suchthat the respective tables span columns of the another table with whichdata of the respective tables are unassociated; and modifying a settingof a display attribute of a first column of a first one of therespective tables from a first setting to a second setting based onmodification of a setting of a display attribute of a first column of asecond one of the respective tables based on a stored rule that providesfor at least a portion of the first column of the first one of therespective tables and a portion of the first column of the second one ofthe respective tables to be vertically aligned, one beneath the other,when displayed in the displaying step, wherein a column arrangement ofthe first one of the respective tables is different than a columnarrangement of the second one of the respective tables.
 10. The methodof claim 9, wherein the display attribute of the first column includesat least one of a size and a display position.
 11. The method of claim9, further comprising: determining that the first column of the firstone of the respective tables corresponds for alignment to the firstcolumn of the second table; wherein: the correspondence is determinedbased on one of: (a) a similarity of a data type between content of thefirst column of the first one of the respective tables and the firstcolumn of the second one of the respective tables, (b) a link betweenthe first column of the first one of the respective tables and the firstcolumn of the second one of the respective tables set in accordance witha user input instruction, and (c) a shared column ID between the firstcolumn of the first one of the respective tables and the first column ofthe second one of the respective tables; and the setting of the displayattribute of the first column of the first one of the respective tablesbased on the display attribute of the first column of the second one ofthe respective tables is performed conditional upon the determining thatthe first column of the first one of the respective tables correspondsfor alignment to the first column of the second table.
 12. Anon-transitive computer-readable medium having stored thereoninstructions adapted to be executed by a processor, the instructionswhich, when executed, cause the processor to perform a method fordisplaying hierarchically related data, the method comprising:simultaneously displaying in a display window respective representationsof a plurality of hierarchically related data records in accordance withthe hierarchical relationship; wherein: each of at least two of therepresentations includes a respective table, the respective tableincluding: a respective plurality of data columns; a respective columnheader row that includes column headers identifying a respectiveplurality of categories to which the data columns correspond; and one ormore respective additional rows including data indicated to beassociated with the categories of the respective column header row ofthe table to which the plurality of additional rows belongs by displayof the data beneath the column headers of the respective column headerrow; the at least two representations' represented data records dependfrom a common ancestor data record; the respective tables are displayed(a) nested in another table representing the ancestor data record, and(b) such that the respective tables span columns of the another tablewith which data of the respective tables are unassociated; the anothertable representing the ancestor record includes a single column headerrow, displayed simultaneously with the column header row of at least oneof the at least two representations, and that includes column headersidentifying a respective plurality of categories to which the columns ofthe another table correspond; the another table includes a data row that(a) includes data populating fields formed by an intersection of thedata row of the another table with the columns of the another table and(b) is displayed below the at least one of the at least tworepresentations; and the single column header row is displayed above thetables of the at least two representations and is not repeated below anyof the at least two representations.
 13. A system for displayinghierarchically related data, comprising: a display device; and aprocessor configured to: display in a display window of the displaydevice respective representations of a plurality of hierarchicallyrelated data records in accordance with the hierarchical relationship;wherein: each of at least two of the representations includes arespective table, the respective table including: a respective pluralityof data columns; a respective column header row that includes columnheaders identifying a respective plurality of categories to which thedata columns correspond; and one or more respective additional rowsincluding data indicated to be associated with the categories of therespective column header row of the table to which the plurality ofadditional rows belongs by display of the data beneath the columnheaders of the respective column header row; the at least tworepresentations' represented data records depend from a common ancestordata record; the respective tables are displayed nested in another tablerepresenting the ancestor data record, and are not arranged within anycommon row of the another table; the another table representing theancestor record includes a single column header row, displayedsimultaneously with the column header row of at least one of the atleast two representations, and that includes column headers identifyinga respective plurality of categories to which the columns of the anothertable correspond; the another table includes a data row that (a)includes data populating fields formed by an intersection of the datarow of the another table with the columns of the another table and (b)is displayed below the at least one of the at least two representations;and the single column header row is displayed above the tables of the atleast two representations and is not repeated below any of the at leasttwo representations.
 14. The system of claim 13, wherein the respectivetables differ from each other with respect to at least one of a numberof included columns, data categories represented by respective columns,data types included in respective columns, and an order in whichrespective columns are arranged.
 15. The system of claim 13, wherein adisplayed representation includes a plurality of tables, each tableincluding data records of a hierarchical level that is one lower thanthat of the data record represented by the displayed representation. 16.The system of claim 13, wherein: the processor is configured to display,for each of at least one of the hierarchically related data records, acontrol to toggle between an expanded and collapsed view of therespective one of the respective data records; when the expanded view isactive, a table including child data records of the respective datarecord is displayed; and when the collapsed view is active, the table isnot displayed.
 17. A system for displaying hierarchically related data,comprising: a display device; and a processor configured to: display ina display window of the display device respective representations of aplurality of hierarchically related data records in accordance with thehierarchical relationship, wherein: each of at least two of therepresentations includes a respective table, the respective tableincluding: a respective plurality of data columns; a respective columnheader row that includes column headers identifying a respectiveplurality of categories to which the data columns correspond; and one ormore respective additional rows including data indicated to beassociated with the categories of the respective column header row ofthe table to which the plurality of additional rows belongs by displayof the data beneath the column headers of the respective column headerrow; the at least two representations' represented data records dependfrom a common ancestor data record; and the respective tables aredisplayed nested in another table representing the ancestor data record,and are not arranged within any common row of the another table; and seta display attribute of a first column of a first one of the respectivetables based on a display attribute of a first column of a second one ofthe respective tables so that at least a portion of the first column ofthe first one of the respective tables and a portion of the first columnof the second one of the respective tables are vertically aligned, onebeneath the other, when displayed in the display window, wherein acolumn arrangement of the first one of the respective tables isdifferent than a column arrangement of the second one of the respectivetables.
 18. The system of claim 17, wherein the display attribute of thefirst column includes at least one of a size and a display position. 19.The system of claim 17, wherein: the processor is configured todetermine that the first column of the first one of the respectivetables corresponds for alignment to the first column of the secondtable; the correspondence is determined based on one of: (a) asimilarity of a data type between content of the first column of thefirst one of the respective tables and the first column of the secondone of the respective tables, (b) a link between the first column of thefirst one of the respective tables and the first column of the secondone of the respective tables set in accordance with a user inputinstruction, and (c) a shared column ID between the first column of thefirst one of the respective tables and the first column of the secondone of the respective tables; and the setting of the display attributeof the first column of the first one of the respective tables based onthe display attribute of the first column of the second one of therespective tables is performed conditional upon the processordetermining that the first column of the first one of the respectivetables corresponds for alignment to the first column of the secondtable.
 20. A computer-implemented method comprising: providing, b acomputer processor, data for transmission, the data includinginstructions adapted to be executed by a processor, the instructionswhich, when executed, cause the processor to perform a method fordisplaying hierarchically related data, the method for displayingcomprising: simultaneously displaying in a display window respectiverepresentations of a plurality of hierarchically related data records inaccordance with the hierarchical relationship; wherein: each of at leasttwo of the representations includes a respective table, the respectivetable including: a respective plurality of data columns; a respectivecolumn header row that includes column headers identifying a respectiveplurality of categories to which the data columns correspond; and one ormore respective additional rows including data indicated to beassociated with the categories of the respective column header row ofthe table to which the plurality of additional rows belongs by displayof the data beneath the column headers of the respective column headerrow; the at least two representations' represented data records dependfrom a common ancestor data record; the respective tables are displayed(a) nested in another table representing the ancestor data record, and(b) such that the respective tables span columns of the another tablewith which data of the respective tables are unassociated; the anothertable representing the ancestor record includes a single column headerrow, displayed simultaneously with the column header row of at least oneof the at least two representations, and that includes column headersidentifying a respective plurality of categories to which the columns ofthe another table correspond; the another table includes a data row that(a) includes data populating fields formed by an intersection of thedata row of the another table with the columns of the another table and(b) is displayed below the at least one of the at least tworepresentations; and the single column header row is displayed above thetables of the at least two representations and is not repeated below anyof the at least two representations.